#2111 - Disable telemetry in DD agent and application #2187
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR sets
DD_INSTRUMENTATION_TELEMETRY_ENABLED
in our app andDD_APM_TELEMETRY_ENABLED
in the DD agent to false. According to Datadog support, and their documentation, those two env vars are set to true by default, but the federal govt datadog URL does not support those features.When those are set to true, our DD agent attempts to make calls to the telemetry endpoint, which doesn't exist, causing 404 throttling errors in our logs.
For reference: https://docs.datadoghq.com/tracing/configure_data_security/?tab=environmentvariables&site=gov#telemetry-collection
issue #2111
How Has This Been Tested?
Successful perf deploy here: https://github.com/department-of-veterans-affairs/notification-api/actions/runs/12399618902
I deployed this change to perf and those throttling error logs lines are now gone.
The deploy finished at around 2:15pm ET and those log items stopped showing up at around 2:19pm ET.
Checklist